EnWater Design
Project report packs

Project Report Packs for Decisions, Approvals and Delivery

Each Report Pack records the technical basis, decisions, responsibilities and review requirements for a specific project point. A report can stand alone or connect with a Technical Study, Process Design Pack, Sourcing Advisory or implementation support.

Matched to the current project point Standalone or connected Decisions and requirements kept traceable
How the report packs are grouped

This is the project-point view of the Report Packs introduced on How We Engage:

  • Early direction: project background and feasibility.
  • Procurement basis: implementation alignment and supplier support.
  • Performance follow-through: commissioning, review and performance improvement.

The examples below show common groupings such as Project Background & Early Direction, Feasibility & Planning, Implementation Alignment, and Commissioning & Performance. They are not a required sequence; a single report or a different combination can be defined around the project need.

Report points at a glance
Early direction · Project background

Project Background & Early Direction Pack

The Project Background & Early Direction Pack creates a shared project background before feasibility, design or supplier engagement. It records the problem, existing conditions, project boundary and information needed for the next decision.

What it covers: water, wastewater and residuals sources; existing assets and constraints; compliance or approval requirements; reuse or recovery objectives; known assumptions; and the initial information plan.

Starting point: a documented basis is needed for internal alignment, approval discussions or a later Technical Study.

Typical reports in this pack
  • Project Background Report
  • Regulatory Alignment Note
  • Information and Data-Gap Plan

These reports can be issued together or separately. They establish the background and requirements for the next decision without committing the project to a treatment route.

Supports the decision on: whether the project basis is sufficiently clear, what requires confirmation and whether a Technical Study, Process Design Pack or another focused assignment is needed next.

Typical project drivers
What usually prompts a Project Background & Early Direction Pack.
Approval or planning requirement
A concise project background is needed for internal or external review.
Conflicting project assumptions
Teams are working from different boundaries, objectives or source information.
Baseline information gaps
Data, drawings or operating records are incomplete, inconsistent or out of date.
Owner and planning-led
Early direction · Route and feasibility

Feasibility & Planning Pack

The Feasibility & Planning Pack compares the relevant routes and documents the basis for selecting one. It can be developed from an existing study or connected to a Technical Study where the route, cost basis or a major technical decision remains open.

What it covers: decision criteria, confirmed inputs, route alternatives, technical and lifecycle implications, order-of-magnitude CAPEX and OPEX where required, risks, data gaps and phasing considerations.

Decision point: an owner, board, lender or project team needs a documented route decision before process design or procurement.

Typical reports in this pack
  • Options Comparison Matrix
  • Feasibility Assessment
  • Route and Phasing Note

The reports may be combined as a Project Feasibility Report or issued separately to match the approval point.

Supports the decision on: which route to carry forward, what level of reuse or recovery is justified and what must be confirmed to provide a sufficient basis for process design or procurement.

Typical project drivers
Why feasibility & route work is usually commissioned.
Board, lender or internal approval
A clear route decision is needed, supported by technical and cost ranges.
Upgrade, retrofit or replacement uncertainty
The project has not established whether existing assets should be retained, modified or replaced.
Reuse or recovery objective
The achievable duty, cost implications and residuals route need to be established.
Owner, finance and project-led
Procurement basis · Implementation alignment

Implementation Alignment Pack

The Implementation Alignment Pack translates an agreed technical basis into the requirements, responsibilities and review criteria needed for supplier engagement. It does not replace the Process Design Pack where process calculations, process flow diagrams and equipment duties still need to be developed.

What it covers: process requirements, package boundaries, connections, controls intent, supplier returns, verification requirements and technical review points.

Procurement preparation: an RFP, Terms of Reference or supplier request must be prepared from an established technical basis.

Typical reports in this pack
  • Scope or Terms of Reference Requirements
  • Responsibility and Coordination Matrix
  • Supplier Return and Evaluation Requirements

These reports can use an existing Process Design Pack or another agreed technical basis and form the technical foundation for sourcing.

Supports the decision on: what suppliers are being asked to provide, how responsibilities are divided and what information is needed for comparable technical submissions.

Typical project drivers
Why implementation alignment support is usually needed.
Tender or RFQ preparation
Technical requirements must be issued without over-prescribing the supplier's design.
Connection risk
Boundaries between the owner, EPC and equipment suppliers are unclear.
Performance clarity before contract
Testing and performance evidence need to be defined before award.
Technical and procurement-led
Procurement basis · Supplier selection

Vendor & Contracting Support Pack

The Vendor & Contracting Support Pack records the technical evaluation, clarifications and contract requirements developed during supplier selection. It supports Sourcing Advisory while procurement, commercial and legal decisions remain with the client.

What it covers: supplier departures, alternatives, exclusions, technical evaluation, clarification responses, recommended technical conditions and contract schedules.

Selection and award: the client or evaluation committee needs a traceable technical basis for supplier selection and award.

Typical reports in this pack
  • Technical Evaluation Matrix
  • Clarification and Deviation Register
  • Technical Recommendation and Contract Schedule

These records can be issued as one Vendor Selection Report or as separate documents matched to the client’s procurement process.

Supports the decision on: which submission best meets the agreed requirements and which technical conditions must be closed before contract.

Typical project drivers
What usually brings owners to supplier-selection support.
Non-comparable proposals
Supplier assumptions, exclusions and alternatives prevent a consistent technical comparison.
CAPEX and lifecycle concern
The lowest-priced offer may not provide the best operating or lifecycle outcome.
Award and approval scrutiny
The selection needs a traceable technical basis, with major departures and risks resolved.
Procurement and approvals-led
Performance follow-through · Commissioning

Commissioning & Performance Pack

The Commissioning & Performance Pack defines the requirements and records needed to check the supplied system through commissioning, performance testing and transition to normal operation. Active commissioning support is a separate implementation assignment where required.

What it covers: pre-commissioning checks, test conditions, sampling, acceptance criteria, responsibilities, required records and operating transition.

Verification and handover: an awarded or completed system needs an agreed basis for verification, handover or receiving-party acceptance.

Typical reports in this pack
  • Commissioning & Start-up Alignment Note
  • Performance Test and Monitoring Plan
  • Handover and Early-Operation Requirements

The pack can be prepared before commissioning or used to consolidate the agreed requirements and records during implementation support.

Supports the decision on: what must be demonstrated, how evidence is recorded and what remains open before handover or acceptance.

Typical project drivers
Why commissioning and performance support is usually formalised.
Regulatory or contractual handover
Evidence is needed that the completed system meets permit, contract or performance requirements.
Operator readiness
Operators need a clear basis for start-up, early issues and handover.
Milestone or performance payment
Test results are linked to acceptance, release of payment or contract closure.
Owner, operator and regulator-led
Performance follow-through · Improvement

Performance Improvement Pack

The Performance Improvement Pack reviews operating evidence after handover and records the actions needed to stabilize performance, improve efficiency or assess a further investment. Where a further reuse, residuals, automation or investment decision remains open, it can connect to a Technical Study.

What it covers: operating records, performance against design criteria, cost and resource use, recurring constraints, optimization actions and options requiring further study.

Operating review: an owner or operator needs a documented performance assessment, corrective-action basis or next investment decision.

Typical reports in this pack
  • Performance and Resilience Review
  • Performance Improvement Action Plan
  • Further Study or Investment Note

A further decision can be defined through a Technical Study or other focused assignment rather than assuming the next route.

Supports the decision on: whether to maintain the current operating basis, implement defined adjustments or commission further assessment.

Typical project drivers
When performance-improvement work becomes worth assessing.
Delivered performance check
Results need to be compared with the original design and performance basis.
Cost or resource pressure
Chemical, energy, water or residuals costs are increasing or no longer acceptable.
Further reuse or recovery opportunity
A new duty or investment is being considered from the operating basis.
Asset, operations and finance-led

Define the report needed now

A Report Pack does not require the project to begin with the first example or continue through every later pack. We review the available studies, designs, supplier information and operating records, then define the report or combination required for the current decision, approval or review point.

Where the report identifies a need for analysis or process design, or for sourcing or implementation support, that scope is defined separately rather than folded into the report by default.

Share the project point, required decision or approval, and the information already available. We will respond with the proposed report scope, inputs and responsibilities.

Continue to contact form Review Technical Studies